Remote management of electronic products

ABSTRACT

A remote server may receive a data log with information regarding the status and/or a setting of an electronic product. The remote server may store information in the data log in a database. The remote server may process information in the database to determine whether a newer version of firmware is available for the electronic product is available.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. Provisional PatentApplication No. 61/644,386, filed on May 8, 2012, which is herebyincorporated by reference in its entirety.

BACKGROUND

The present application generally relates to electronic products, andmore particularly, but not exclusively, relates to a system for managingelectronic products.

Electronic products and/or information about the electronic products maybe managed in various ways. Some existing management systems havevarious shortcomings relative to certain applications. Accordingly,there remains a need for further contributions in this area.

SUMMARY

One embodiment of the present application is a system for remotemanagement of an electronic product. Other embodiments includeapparatuses and methods for remotely managing an electronic product.Further embodiments of the present application will become apparent fromthe description and figures that follow.

BRIEF DESCRIPTION OF THE FIGURES

The description herein makes reference to the accompanying figureswherein like reference numerals refer to like parts throughout theseveral views, and wherein:

FIG. 1 is a schematic block diagram of an exemplary system.

FIG. 2 is an illustration of an exemplary data log.

FIG. 3 is a schematic block diagram of an exemplary computing device.

FIG. 4 is a schematic flow diagram of process for managing informationin an electronic product.

DETAILED DESCRIPTION OF THE ILLUSTRATIVE EMBODIMENTS

For the purposes of promoting an understanding of the principles of thepresent invention, reference will now be made to the embodimentsillustrated in the drawings and specific language will be used todescribe the same. It will nevertheless be understood that no limitationof the scope of the invention is thereby intended. Any alterations andfurther modifications in the described embodiments, and any furtherapplications of the principles of the invention as described herein arecontemplated as would normally occur to one skilled in the art to whichthe invention relates.

FIG. 1 is a schematic block diagram of an exemplary system 100 forremotely managing an electronic product. The system 100 includeselectronic products such as one or more offline electronic locks 102,e.g., for a door. It is contemplated that online electronic locks and/orother types of electronic products may be used with the presentapplication. The offline electronic locks 102 may be part of an accesscontrol system at a customer site such as a building.

The offline electronic lock 102 is structured to store statusinformation, setting(s), configuration(s), and/or other data 103 aboutthe offline electronic lock 102. A mobile device 106 is structured toacquire the status information, setting(s), configuration(s), and/orother data 103 from the offline electronic lock 102 via a wired orwireless connection. The mobile device 106 may use any application orprotocol for communicating with an offline electronic lock 102. Oneexample is the Schlage Utility Software (SUS); however, otherapplications are contemplated.

The mobile device 106 is structured to generate a product data log 104based on the status information, setting(s), configuration(s), and/orother data 103 acquired from the offline electronic lock 102. FIG. 2illustrates an exemplary product data log 104, which may include thestatus information and the settings of the electronic lock 102. Forexample, the product data log 104 may include one or more of thefollowing information or settings: serial number(s) (e.g., main serialnumber, reader serial number), model type, motor cycles, cycles sincebattery change, last sync time, born date (e.g., main born date orreader born date), days since use, main hardware version, firmware(s) inuse (e.g., main firmware version, main bootloader version, readerfirmware version, reader bootloader version), battery type (e.g., 4pack), main battery (e.g., charge in volts), lithium battery (e.g.,charge in volts), PIN length, ignore keypad, record lock/unlock, devicelocation, end user contact, power status, system settings, hardwarerevision(s), date of manufacture, and/or “days since installation.” Itis contemplated that other information or settings of the offlineelectronic lock 102 may be stored in the product data log 104. It iscontemplated that in some embodiments the offline electronic lock 102generates the product data log 104 and transmits it to the mobile device106.

The mobile device 106 may be a personal digital assistant (PDA) (e.g., aBluebird Pidion), a smartphone, a tablet computer, a laptop computer,and/or any other type of mobile computing device. The connection betweenthe offline electronic lock 102 and the mobile device 106 may be made byany suitable or supported protocol. The mobile device 106 is structuredto store the product data log 104 in memory in the mobile device 106.Typically, a user will walk around to the various offline electroniclocks 102 so that the mobile device 106 and the offline electronic locksmay interact with one another.

A user of the mobile device 106 may view the product data log 104 on themobile device 106. It is contemplated that the mobile device 106 maystore multiple product data logs 104 such as one log for each electronicproduct the mobile device 106 interacted with or the mobile device 106may store one master product data log 104 that includes information formultiple electronic products. In some embodiments, repeatedcommunications with the same electronic product will result in only thelatest entry being stored for that product.

The mobile device 106 is structured to transmit the product data log 104to a local computer 108 via wired or wireless connection. The connectionbetween the mobile device 106 and the local computer 108 may be made byany suitable or supported protocol. For example, this may beaccomplished automatically using Microsoft sync utilities such asActiveSync or Windows Mobile Device applications based on the particularoperating system used on a user's local computer 108. Some syncutilities use a shared folder on the local computer 108 to exchange data(e.g., product data log 104) between the mobile device 106 and the localcomputer 108.

The local computer 108 is generally located in the same building or onthe same campus as the electronic locks 102. The local computer 108 isstructured to store the product data log 104 and/or information from theproduct data log 104 in a customer data log 110 on the local computer108. The customer data log 110 may include information about thecustomer such as contact information, status information and settingsfor some or all of the electronic products at the customer's site(s),and any other type of customer information. A user of the local computer108 may view the product data log 104 or the customer data log 110 onthe local computer 108.

The local computer 108 is structured to transmit at least a portion ofthe product data log 104 and/or the customer data log 110 to a remoteserver 112 automatically or when requested or selected by a user of thelocal computer 108. The remote server 112 may be maintained by amanufacturer of the electronic products. The local computer 108 and theremote server 112 may communicate with one another over the Internetthrough a cloud or web interface. For example, the local computer 108may include an application 113, which upon start-up will log into theremote server 112 using, e.g., an administrator name, location, contactinformation, password, and/or any other information. During daily use,the application 113 may monitor the shared folder used by the localcomputer 108 and the mobile device 106 and send any new product data log104 (as part of or instead of customer data log 110) to the remoteserver 112.

Furthermore, if a customer site is using multiple mobile devices 106 tomanage their facility, the local computer 108 may append the facilityand contact information to each product data log 104 before sending theproduct data log 104 to the remote server 112 to ensure that all of theproduct data logs 104 are uniquely identified as belonging with thatfacility.

As another example, the local computer 108 may include a web browser,which communicates with a web page and/or web portal on the remoteserver 112 via the Internet. However, other communication channelsand/or mediums are contemplated. The remote server 112 may be part ofcloud service for remotely managing electronic products. Furthermore,although the remote server 112 is shown as one server in FIG. 1, theremote server 112 may be comprised of multiple servers. The remoteserver 112 is typically located at a site that is remote from thecustomer's site and the local computer 108. It is contemplated that theremote server 112 is located at the same site as the local computer 108.

The remote server 112 is structured to store information from thecustomer data log 110 in a database 114 at the remote server 112 such aselectronic product information and customer information. The database114 may store electronic product information for multiple customers.

The remote server 112 is structured to process electronic productinformation in the database 114 to determine whether a newer version offirmware is available for an electronic product such as the electroniclock 102. For example, the remote server 112 may compare the latestversion number of firmware to the firmware version number for eachproduct in the database 114 to determine if a new version of firmware isavailable. The remote server 112 may set a flag in the database 114indicating that an electronic product or a particular customer siteshould receive a firmware update. If a new version of firmware isavailable, the remote server 112 may automatically transmit or push afirmware package 116, which includes the particular firmware for theoffline electronic lock 102, to the local computer 108. For example,whenever the local computer 108 is logged into the remote server 112,any new versions of firmware may be automatically downloaded to thelocal computer 108 without any user request, selection, or interaction.The new firmware may downloaded and stored in the shared folder on thelocal computer 108 that is used by the mobile device 106 to exchangedata with the local computer 108. The firmware package 116 may also beemailed from the remote server 112 to the local computer 108.

It is contemplated, however, that a new version of firmware may besuggested by the remote server 112, or a new version of firmware may bepulled from the remote server 112 by the local computer 108.Furthermore, whether a firmware package is pushed, suggested, or pulledis a setting that may be configured in the customer preferences in theweb interface of the remote server 112 or in the application 113.

Furthermore, a firmware update may be suggested by, e.g., a pop-upmessage. There may be various levels of messages. For example, there maybe a “must update” message when there would be firmware versionconflicts if an update is not done or if there is a liability orsecurity issue identified. Another message may be “should update” whenthere are improvements available and/or new or changed features. Anothermessage may be “no need to update” when the updates are miscellaneous,cosmetic, and/or minor. Another message may be “contact your OEMsupplier before updating” when OEMs will want to test and approve anupdate first. Another potential feature is turning off automaticupdating and/or prompts if a customer chooses to do so.

It is contemplated that release note(s) may be included in the firmwarepackage 116 to inform the user of what has changed. The release notesmay be viewed on the mobile device 106, on the local computer 108,and/or the remote server 112.

Once a firmware package 116 has been downloaded to the local computer108, at least a portion of the firmware package 116 is transmitted tothe mobile device 106 as described above by using standard utilitiesand/or a shared folder. In addition, the firmware package 116 may bepushed or automatically transferred to the mobile device 106 without auser requesting the data. It is contemplated that the mobile device 106and/or the local computer 108 may prompt a user before transmitting thefirmware data to the mobile device 106. Once the mobile device 106 hasthe new firmware data, the user of the mobile device 106 may update thefirmware in the offline electronic lock 102 with data from the firmwarepackage 116.

In addition, the mobile device 106 may be configured to provide one ormore of the following features: accept new firmware packages 116 fromthe local computer 108 when “synced”; place the new firmware into the“root” directory of the mobile device 106 so that the firmware isreadily available if/when a firmware update is needed on an offlineelectronic lock 102; and upon connection with an offline electronic lock102, inform the user of the mobile device 106 that a firmware update isavailable, when the customer's offline electronic lock 102 is notrunning the latest firmware.

As seen in FIG. 1, the system 100 may include other computing devicessuch as another mobile device 118 and another computer 120. The othercomputing devices 118, 120 may connect to the remote server 112 via theInternet through a web interface. For example, the mobile device 118 andcomputer 120 may include web browsers that communicate with a web pageor web portal on the remote server 112 to monitor electronic products,adjust settings, adjust preferences, change contact information, and/orview the data stored in the database 114. It is contemplated that themobile device 118 may include an app that provides communication betweenthe mobile device 118 and the remote server 112 rather than a webbrowser. The mobile device 118 and the computer 120 may be operated by acustomer or by the manufacturer that maintains the remote server 112.Generally, a customer may only view or change the data associated withtheir site(s) and/or product(s). A customer generally cannot view orchange another customer's data.

The remote server 112 may be structured to analyze the information inthe database 114 to determine whether any preventative maintenanceshould be performed on the offline electronic lock 102. For example,based on particular field in the database 114 such as “cycles sincebattery change” may indicate that the battery in the offline electroniclock 102 should be replaced. If the remote server 112 determines thatpreventative maintenance should be performed, the remote server 112 maytransmit a notification to the local computer 108. Typically, thenotification identifies the type of preventative maintenance to beperformed. The notification may be an email, a short message service(SMS) message, and/or a message viewable on a web page, web portal,and/or web interface hosted by the remote server 112. Other types ofnotifications are contemplated.

Users with access to the information in database 114 may provide bettertechnical support of the offline electronic locks 102. For example, atechnical support specialist would have access to technical informationabout how the particular electronic lock 102 has been operating,settings, status, firmware(s) version, hardware versions, systemcomponents, among other data to use in troubleshooting issues.

The remote server 112 may be structured to analyze information in thedatabase 114 to determine whether any warranty exists on a particularproduct and/or whether any warranty replacement parts should bedistributed to a customer. If a warranty exists and warranty replacementparts should be provided to a customer, the remote server 112 maytransmit a notification to the customer based on customer contactinformation in the database 114. The notification may be an email, ashort message service (SMS) message, and/or a message viewable on a webpage, web portal, and/or web interface hosted by the remote server 112.Other types of notifications are contemplated. The present applicationgenerally allows the manufacturer, distributor, dealer, and/or end-userto know if product is in its warranty earlier rather than when a productis returned for analysis, which may be when the product is out of itswarranty period.

In some embodiments, the mobile device 106 may transmit the product datalog 104 directly to the remote server 112 via email or an applicationthat uses the Internet. For example, the mobile device 106 may connectto the Internet using a wireless technology such as WiFi, Bluetooth, acell phone data network, and/or any other technology for a mobile deviceto connect to the Internet. Furthermore, in some embodiments, the mobiledevice 106 may download the latest firmware packages directly from theremote server 112 via the Internet as discussed above.

By having access to the information about how the electronic productsare used, the manufacturer may facilitate and improve sales as well asdealer and customer relationships. In addition, if the manufacturertypically sells to distributor and/or dealer, the system 100 may providethe manufacturer the opportunity to communicate with end usersproactively (e.g., preventative maintenance) and reactively (e.g.,technical support when there is an issue). The information in thedatabase 114 may reduce liability in critical life safety situations.

The information in the database 114 may be used by the electronicproduct manufacturer for future design improvements and predictiveanalysis. The manufacturer may also learn from the information in thedatabase 114 which settings are actually being used and knowing thosesettings that are never used, which may affect future product designsand/or features. For example, if a setting or feature is usedfrequently, then it is likely that that setting or feature will bepresent in future products. Similarly, if a setting or feature is usedinfrequently, then it is less likely that that setting or feature willappear in future products.

The present application may reduce technical service calls becauseend-users are using electronic products that are programmed withuntested firmware version combinations. For example, wholesalers anddealers who buy product now and re-class devices or resell at a laterdate with newer devices. The present application may reduce theinability or difficulty in locating installed products for recalls orcritical bug fixes. The present application may provide data readilyavailable to technical support services personnel for troubleshootingand isolation of a problem in the field. The present application mayallow the manufacturer of the electronic product identify who their realend-users are. The present application may allow the manufacturer todetermine how the electronic products are used, e.g., how do healthcare,commercial, and education environments differ, if at all? The presentapplication may prevent or reduce customer dissatisfaction when aproduct is returned as warranty, but later found to be “out of warranty”because the product may returned or fixed earlier while the warranty isstill running The present application may prevent or reduce multipleproduct firmware versions at a single site resulting in inconsistentproduct performance. The present application may be prevent or reducedisparate behaviors due to “Phased-IN” purchase and installation timingsuch as user interface and functionality differences when a productbought last year is mixed with new products purchased this year. Theremote server 112 may provide up to the minute technical bulletins andtechnical notifications direct to its customers.

FIG. 3 is a schematic diagram of a computing device 200. The computingdevice 200 is one example of a electronic product, mobile device,computer, and/or server, which may be utilized in connection with theoffline electronic lock 102, mobile device 106, local computer 108,remote server 112, mobile device 118, and/or computer 120 shown inFIG. 1. Computing device 200 includes a processing device 202, aninput/output device 204, memory 206, and operating logic 208.Furthermore, computing device 200 communicates with one or more externaldevices 210.

The input/output device 204 may be any type of device that allows thecomputing device 200 to communicate with the external device 210. Forexample, the input/output device 204 may be a transceiver (e.g., WIFI,NFC, Bluetooth), network adapter, network card, interface, or a port(e.g., a USB port, serial port, parallel port, an analog port, a digitalport, VGA, DVI, HDMI, FireWire, CAT 5, or any other type of port orinterface). The input/output device 204 may be comprised of hardware,software, firmware, and/or state machines. It is contemplated that theinput/output device 204 may include more than one transceiver, networkadapter, network card, or port.

The external device 210 may be any type of device that allows data to beinputted to or outputted from the computing device 200. For example, theexternal device 210 may be an electronic product (e.g., an offlineelectronic lock), a transceiver, a mobile device, an accessory, a readerdevice, equipment, a handheld computer, a diagnostic tool, a controller,a computer, a server, a processing system, a sensor, a printer, adisplay, an alarm, an illuminated indicator such as a status indicator,a keyboard, a mouse, or a touch screen display. Furthermore, it iscontemplated that the external device 210 may be integrated into thecomputing device 200. For example, the computing device 200 may be amobile phone, a handheld diagnostic tool, a smartphone, a laptopcomputer, or a tablet computer in which case the display would be anexternal device 210, but the display is integrated with the computingdevice 200 as one unit, which is consistent with the general design ofmobile phones, handheld diagnostic tools, smartphones, laptop computers,tablet computers, and the like. It is further contemplated that theremay be more than one external device in communication with the computingdevice 200. The computing device 200 is one example of an externaldevice 210.

Processing device 202 can be a programmable type, a dedicated, hardwiredstate machine; or a combination of these; and it can further includemultiple processors, Arithmetic-Logic Units (ALUs), Central ProcessingUnits (CPUs), Digital Signal Processors (DSPs), or the like. Processingdevices 202 with multiple processing units may utilize distributed,pipelined, and/or parallel processing. Processing device 202 may bededicated to performance of just the operations described herein or maybe utilized in one or more additional applications. In the depictedform, processing device 202 is of a programmable variety that executesalgorithms and processes data in accordance with operating logic 208 asdefined by programming instructions (such as software or firmware)stored in memory 206. Alternatively or additionally, operating logic 208for processing device 202 is at least partially defined by hardwiredlogic or other hardware. Processing device 202 can be comprised of oneor more components of any type suitable to process the signals receivedfrom input/output device 204 or elsewhere, and provide desired outputsignals. Such components may include digital circuitry, analogcircuitry, or a combination of both.

Memory 206 may be of one or more types, such as a solid-state variety,electromagnetic variety, optical variety, or a combination of theseforms. Furthermore, memory 206 can be volatile, nonvolatile, or amixture of these types, and some or all of memory 206 can be of aportable variety, such as a disk, tape, memory stick, cartridge, or thelike. In addition, memory 206 can store data that is manipulated by theoperating logic 208 of processing device 202, such as datarepresentative of signals received from and/or sent to input/outputdevice 204 in addition to or in lieu of storing programming instructionsdefining operating logic 208, just to name one example. As shown in FIG.3, memory 206 may be included with processing device 202 and/or coupledto the processing device 202. Memory 206 is one example of a computerreadable medium.

FIG. 4 is a schematic flow diagram of a process 400 for managing anelectronic product. Operations illustrated for all of the processes inthe present application are understood to be examples only, andoperations may be combined or divided, and added or removed, as well asre-ordered in whole or in part, unless explicitly stated to thecontrary.

The process 400 may be implemented in operating logic 208 as operationsby software, hardware, artificial intelligence, fuzzy logic, or anycombination thereof, or at least partially performed by a user oroperator. In certain embodiments, modules represent software elements asa computer program encoded on a computer readable medium, wherein acomputing device 200 performs the described operations when executingthe computer program.

Process 400 begins at operation 402 in which data is acquired from aproduct. For example, the mobile device 106 may receive statusinformation, setting(s), configuration(s), and/or other data 103 fromthe offline electronic lock 102 and generate a product data log 104.

Process 400 then proceeds from operation 402 to operation 404. Atoperation 404 the mobile device 106 transfers the product data log 104to the local computer 108 as discussed above.

Process 400 then proceeds from operation 404 to operation 406. Atoperation 406 the local computer 108 transfers at least a portion of theproduct data log 104 and/or a customer data log 110 to the remote server112 as discussed above.

Process 400 then proceeds from operation 406 to operation 408. Atoperation 408 the remote server 112 analyzes the information stored inthe database 114 to determine whether any product needs a firmwareupdate, whether any product needs any preventative maintenance, orwhether any other action should be take based on an analysis of theinformation in the database 114. If the remote server 112 determinesthat an action should be taken then process 400 proceeds from operation408 to operation 410 in which the action (e.g., firmware update,preventative maintenance) is taken. After the action is taken, theremote server 112 may continues its analysis of the information andawait new product data. If the remote server 112 determines that noaction should be taken, the process 400 proceeds from operation 408 tooperation 412 in which the remote server 112 may continues its analysisof the information and await new product data.

The present application may be implemented on any type of computingdevice and using a variety of different software. For example, thepresent application may be implemented using any database system, anysoftware, or any combination thereof. When a computing device 200 isconfigured as a database 114, it is contemplated that the database maybe any type of database, such as relational, hierarchical,object-oriented, and/or the like.

The present application may include one or more of the followingfeatures: capture installed product details and settings; captureend-user and customer contact information; provide productdesign/application analysis opportunities; allow products toautomatically update their operational firmware; and require little orno customer actions to take advantage of the present application.

One aspect of the present application may include a method, comprising:storing lock status information and settings in an electronic lock;transmitting the lock status information and settings from theelectronic lock to a mobile device; storing the lock status informationand settings in a lock data log in the mobile device; transmitting thelock data log from the mobile device to a local computer; storing thelock data log on the local computer; transmitting a customer data logfrom the local computer to a remote server, wherein the customer datalog comprises information from the lock data log; storing informationfrom the customer data log in an electronic product database in theremote server; processing, with the remote server, information in theelectronic product database to determine whether a newer version offirmware is available for the electronic lock; automaticallytransmitting a firmware package from the remote server to the localcomputer; transferring the at least a portion of the firmware packagefrom the local computer to the mobile device; and updating the firmwarein the electronic lock with the at least a portion of the firmwarepackage via the mobile device.

Features of the aspect of the present application may include: whereinthe information is transmitted from the electronic lock to the mobiledevice via one of a wireless connection and a wired connection; pushingthe at least a portion of the firmware package from the local computerto the mobile device when a new version of firmware is available;processing, with the remote server, information in the electronicproduct database to determine whether any preventative maintenanceshould be performed on the electronic lock; transmitting a notificationto the local computer indicating that preventative maintenance should beperformed on the electronic lock, wherein the notification identifies atype of preventative maintenance to be performed; wherein the at least aportion of the firmware package is automatically transferred from thelocal computer to the mobile device without a user requesting the atleast a portion of the firmware package; wherein the lock data logincludes at least one of a serial number, model type, motor cycles,cycles since battery change, last sync time, born date, days since use,firmware version, battery type, battery status, PIN length, ignorekeypad, record lock/unlock, device location, end user contact, powerstatus, hardware revision, date of manufacture, and days sinceinstallation; providing technical support for the electronic lock usinginformation in the electronic product database; processing, with theremote server, the electronic product database to determine whether anywarranty replacement parts should be distributed to a customer; andnotifying the customer of the warranty replacement parts based oncustomer contact information in the electronic product database.

Another aspect of the present application includes a system, comprising:an electronic lock configured to store lock status information andsettings; a mobile device configured to receive the lock statusinformation and settings from the electronic lock and to store the lockstatus information and settings in a lock data log; a local computerconfigured to receive the lock data log from the mobile device and tostore the lock data log; a remote server configured receive a customerdata log from the local computer, wherein the customer data logcomprises information from the lock data log, wherein the remote serveris configured to store information from the customer data log in anelectronic product database in the remote server, wherein the remoteserver is further configured to process information in the electronicproduct database to determine whether a newer version of firmware isavailable for the electronic lock, wherein the remote server is furtherconfigured to automatically transmit a firmware update from the remoteserver to the local computer, wherein the local computer is configuredto automatically transfer the at least a portion of the firmware updateto the mobile device; and wherein the mobile device is configured toupdate the firmware in the electronic lock with the at least a portionof the firmware update.

Features of the aspect of the present application may include: whereinthe information is transmitted from the electronic lock to the mobiledevice via one of a wireless connection and a wired connection; whereinthe remote server is configured to process information in the electronicproduct database to determine whether any preventative maintenanceshould be performed on the electronic lock; wherein the remote server isconfigured to transmit a notification to the local computer indicatingthat preventative maintenance should be performed on the electroniclock, wherein the notification identifies a type of preventativemaintenance to be performed; wherein the lock data log includes at leastone of a serial number, model type, motor cycles, cycles since batterychange, last sync time, born date, days since use, firmware version,battery type, battery status, PIN length, ignore keypad, recordlock/unlock, device location, end user contact, power status, hardwarerevision, date of manufacture, and days since installation; wherein theremote server is configured to process the electronic product databaseto determine whether any warranty replacement parts should bedistributed to a customer, and wherein the remote server is configuredto notify the customer of the warranty replacement parts based oncustomer contact information in the electronic product database.

Yet another aspect of the present application includes an apparatus,comprising: a remote server configured receive a customer data log fromthe local computer, wherein the customer data log comprises informationfrom a lock data log, wherein the lock data log includes statusinformation and settings of an offline electronic lock, wherein theremote server is configured to store information from the customer datalog in an electronic product database in the remote server, wherein theremote server is further configured to process information in theelectronic product database to determine whether a newer version offirmware is available for the offline electronic lock, wherein theremote server is further configured to automatically transmit a firmwareupdate for the offline electronic lock from the remote server to thelocal computer.

Features of the aspect of the present application may include: whereinthe remote server is configured to process information in the electronicproduct database to determine whether any preventative maintenanceshould be performed on the offline electronic lock, and wherein theremote server is configured to transmit a notification to the localcomputer indicating that preventative maintenance should be performed onthe offline electronic lock, wherein the notification identifies a typeof preventative maintenance to be performed.

Another aspect of the present application includes a method, comprising:receiving, with a remote server, a customer data log from the localcomputer, wherein the customer data log comprises information from alock data log, wherein the lock data log includes status information andsettings of an offline electronic lock; storing, with the remote server,information from the customer data log in an electronic productdatabase; processing, with the remote server, information in theelectronic product database to determine whether a newer version offirmware is available for the offline electronic lock; and pushing, withthe remote server, a firmware update for the offline electronic lockfrom the remote server to the local computer.

Features of the aspect of the present application may include:processing, with the remote server, information in the electronicproduct database to determine whether any preventative maintenanceshould be performed on the offline electronic lock; and transmitting,with the remote server, a notification to the local computer indicatingthat preventative maintenance should be performed on the offlineelectronic lock, wherein the notification identifies a type ofpreventative maintenance to be performed; processing, with the remoteserver, information in the electronic product database to determinewhether any warranty replacement parts should be distributed to acustomer; and notifying, with the remote server, the customer of thewarranty replacement parts based on customer contact information in theelectronic product database.

While the invention has been illustrated and described in detail in thedrawings and foregoing description, the same is to be considered asillustrative and not restrictive in character, it being understood thatonly the preferred embodiments have been shown and described and thatall changes and modifications that come within the spirit of theinventions are desired to be protected. It should be understood thatwhile the use of words such as preferable, preferably, preferred or morepreferred utilized in the description above indicate that the feature sodescribed may be more desirable, it nonetheless may not be necessary andembodiments lacking the same may be contemplated as within the scope ofthe invention, the scope being defined by the claims that follow. Inreading the claims, it is intended that when words such as “a,” “an,”“at least one,” or “at least one portion” are used there is no intentionto limit the claim to only one item unless specifically stated to thecontrary in the claim. When the language “at least a portion” and/or “aportion” is used the item can include a portion and/or the entire itemunless specifically stated to the contrary.

1. A method, comprising: storing lock status information and settings inan electronic lock; transmitting the lock status information andsettings from the electronic lock to a mobile device; storing the lockstatus information and settings in a lock data log in the mobile device;transmitting the lock data log from the mobile device to a localcomputer; storing the lock data log on the local computer; transmittinga customer data log from the local computer to a remote server, whereinthe customer data log comprises information from the lock data log;storing information from the customer data log in an electronic productdatabase in the remote server; processing, with the remote server,information in the electronic product database to determine whether anewer version of firmware is available for the electronic lock;automatically transmitting a firmware package from the remote server tothe local computer; transferring the at least a portion of the firmwarepackage from the local computer to the mobile device; and updating thefirmware in the electronic lock with the at least a portion of thefirmware package via the mobile device.
 2. The method of claim 1,wherein the information is transmitted from the electronic lock to themobile device via one of a wireless connection and a wired connection.3. The method of claim 1, further comprising: pushing the at least aportion of the firmware package from the local computer to the mobiledevice when a new version of firmware is available.
 4. The method ofclaim 1, further comprising: processing, with the remote server,information in the electronic product database to determine whether anypreventative maintenance should be performed on the electronic lock. 5.The method of claim 4, further comprising: transmitting a notificationto the local computer indicating that preventative maintenance should beperformed on the electronic lock, wherein the notification identifies atype of preventative maintenance to be performed.
 6. The method of claim1, wherein the at least a portion of the firmware package isautomatically transferred from the local computer to the mobile devicewithout a user requesting the at least a portion of the firmwarepackage.
 7. The method of claim 1, wherein the lock data log includes atleast one of a serial number, model type, motor cycles, cycles sincebattery change, last sync time, born date, days since use, firmwareversion, battery type, battery status, PIN length, ignore keypad, recordlock/unlock, device location, end user contact, power status, hardwarerevision, date of manufacture, and days since installation.
 8. Themethod of claim 1, further comprising: providing technical support forthe electronic lock using information in the electronic productdatabase.
 9. The method of claim 1, further comprising: processing, withthe remote server, the electronic product database to determine whetherany warranty replacement parts should be distributed to a customer; andnotifying the customer of the warranty replacement parts based oncustomer contact information in the electronic product database.
 10. Asystem, comprising: an electronic lock configured to store lock statusinformation and settings; a mobile device configured to receive the lockstatus information and settings from the electronic lock and to storethe lock status information and settings in a lock data log; a localcomputer configured to receive the lock data log from the mobile deviceand to store the lock data log; a remote server configured receive acustomer data log from the local computer, wherein the customer data logcomprises information from the lock data log, wherein the remote serveris configured to store information from the customer data log in anelectronic product database in the remote server, wherein the remoteserver is further configured to process information in the electronicproduct database to determine whether a newer version of firmware isavailable for the electronic lock, wherein the remote server is furtherconfigured to automatically transmit a firmware update from the remoteserver to the local computer, wherein the local computer is configuredto automatically transfer the at least a portion of the firmware updateto the mobile device; and wherein the mobile device is configured toupdate the firmware in the electronic lock with the at least a portionof the firmware update.
 11. The system of claim 10, wherein theinformation is transmitted from the electronic lock to the mobile devicevia one of a wireless connection and a wired connection.
 12. The systemof claim 10, wherein the remote server is configured to processinformation in the electronic product database to determine whether anypreventative maintenance should be performed on the electronic lock. 13.The system of claim 12, wherein the remote server is configured totransmit a notification to the local computer indicating thatpreventative maintenance should be performed on the electronic lock,wherein the notification identifies a type of preventative maintenanceto be performed.
 14. The system of claim 10, wherein the lock data logincludes at least one of a serial number, model type, motor cycles,cycles since battery change, last sync time, born date, days since use,firmware version, battery type, battery status, PIN length, ignorekeypad, record lock/unlock, device location, end user contact, powerstatus, hardware revision, date of manufacture, and days sinceinstallation.
 15. The system of claim 10, wherein the remote server isconfigured to process the electronic product database to determinewhether any warranty replacement parts should be distributed to acustomer, and wherein the remote server is configured to notify thecustomer of the warranty replacement parts based on customer contactinformation in the electronic product database.
 16. An apparatus,comprising: a remote server configured receive a customer data log fromthe local computer, wherein the customer data log comprises informationfrom a lock data log, wherein the lock data log includes statusinformation and settings of an offline electronic lock, wherein theremote server is configured to store information from the customer datalog in an electronic product database in the remote server, wherein theremote server is further configured to process information in theelectronic product database to determine whether a newer version offirmware is available for the offline electronic lock, wherein theremote server is further configured to automatically transmit a firmwareupdate for the offline electronic lock from the remote server to thelocal computer.
 17. The apparatus of claim 16, wherein the remote serveris configured to process information in the electronic product databaseto determine whether any preventative maintenance should be performed onthe offline electronic lock, and wherein the remote server is configuredto transmit a notification to the local computer indicating thatpreventative maintenance should be performed on the offline electroniclock, wherein the notification identifies a type of preventativemaintenance to be performed. 18.-20. (canceled)